
                         Welcome To The Installation Program
                         -----------------------------------

For a complete list of files in this release disk, see DIR.TXT.
For last minutes and resolved issues, see README.TXT.

Clarifications:

         UNIT means Frame Node or Conversion Node
         *    means Any name (BNF context)
		    i.e. */Manager means any Name follows by 
                         the "/Manager" string


TABLE OF CONTENTS
-----------------

 1.  Installation:
     a.  Under */Manager software
     b.  Under */Talk software
     c.  MIBs
 2.  Using TFTP to Upgrade Unit Configurations

1.  INSTALLATION
----------------

    a.  Under The */Manager Software
    --------------------------------

This network management is a Windows application software.

To start the installation, place this disk in Drive A: 
(Drive B: will work as well). Select RUN from the Program
Manager, and enter

    A:\INSTALL

The Installation process requires no input. The application makes certain
that */Manager is already properly installed before copying files to
your hard drive. 

    b.  Under The */Talk Software
    -----------------------------

This network management software is a DOS applcation software.

To start the installation, place this disk in Drive A:, 
change to Drive A: and type INSTALL. (A: is used in this
example but B: will work as well).

>   A:
>   INSTALL

INSTALL works on hard disks only. The INSTALL program will guide
you through the installation process.  

When installation is complete, change your default directory to be the 
directory where your */Talk software was installed(i.e. C:\SNACTALK).

Activate your */Talk software by calling its main executable program,

>   i.e. SYNCTALK 

Once you have connected to a unit, please note that the default password 
for a factory-fresh unit is "sri". It must be entered in lower case.

    c.  MIBs
    --------

MIBS.EXE is a self-extracting compress file. Copy this file to a desired 
directory and type

>   MIBS

Its constained files will be inflated and available for viewing and/or
printing.  The file SRMIB.TXT provides an orientation on the MIBs.


2.  USING TFTP TO UPGRADE UNIT CONFIGURATIONS
-------------------------------------------------

TFTP file receive is supported.  The file transfer should be initiated from
your SNMP manager. The TFTP support allows for one file transfer at a time only.
If a second file transfer is initiated it will be rejected with a reason code 
being resource not available.  A file may be transferred to drive C:, D: or E:.  

Typically, drive D: is reserved for configuration files, drive E: is
reserved for on-line software and dump files.  Drive C: is a RAM drive and
therefore, any files residing on C: will be lost upon reboot of the unit.

The following procedures should be followed for installing new software
and/or configuration.

1. Transfer a file FILES.SYS to drive C: of the unit.  The FILES.SYS file 
   contains the file names and their location for the installation process
   to work properly.  The following is the general format of this file.

      286IMG E:286IMG.TMP
      PARMCFG C:PARMCFG.TMP

   This file may contain only the first entry if only a new software image
   is to be transferred.  It may contain the second entry if only a new
   configuration batch file is to be transferred. Use both entries to
   update both software and configuration. Please see the Users Guide for
   detailed instructions on how to build configurations batch files.

2. Transfer all the files specified in the "FILES.SYS" one at a time to
   their respective destination.  Please note that the file names have a
   ".tmp" extension when transferred to the unit.
 
3. Set the SNMP MIB object "initiateInstall.0" to 1 to begin the
   installation process.  If 286IMG is specified in the FILES.SYS file, the
   NMS(Network Management System) will check the integrity of the
   software by comparing the checksum of the file.  If checksum is okay
   the installation process will begin.  If only the configuration is changed,
   the new configuration will be activated without rebooting the unit.
   If the on-line software is changed, the unit will reboot.  The unit will 
   respond to the manager before rebooting, but under heavy load it is possible
   that the response may not be sent on the LAN before rebooting.

   If there were any errors during installation, an SNMP.ERR file is
   created containing an ASCII error message.  This file may be viewed
   using the DOS TYPE command from NMS.  This file resides on RAM
   drive C:, and will be lost upon reboot.
